queue request
英 [kjuː rɪˈkwest]
美 [kjuː rɪˈkwest]
网络 排队请求
双语例句
- We designed a separate queue in which to place the write request of each user using the order in which they requested the object and enabling the system to process the request accordingly.
我们设计了一个单独队列，根据请求对象的顺序来放置每个用户的写请求，并允许系统处理对应请求。 - We first configure the Queue Connection Factories for both the request and response queues.
我们首先配置请求和响应队列的队列连接工厂。 - This option allows a temporary queue to be recreated to store the response for each request that is sent through the import.
这个选项允许重建一个临时队列来存储通过导入发送的每个请求的响应。 - RMProvider receives a message and inserts this message to the Queue if it is a web service request.
RMProvider接收消息，如果该消息是一个Web服务请求，则就将其插入到Queue中。 - The Java component returns a response message to the defined WebSphere MQ queue via an export with Web service SOAP over JMS binding ( when the request operation is a request/ response operation).
Java组件通过带有Web服务SOAPoverJMS绑定的导出将响应消息返回到定义的WebSphereMQ队列（当请求操作为请求/响应操作时）。 - The queue manager executes one service request within a queue at a given time to maintain integrity.
队列管理器在给定的时间仅执行某个队列中的一个服务请求，以维持完整性。 - JMS Request Queue: The JMS managed object that represents the request MQ queue.
JMS请求队列：表示请求MQ队列的JMS托管对象。 - WebSphere MQ should be already installed on the system, with a queue manager, a request queue, and a reply queue.
WebSphereMQ应该已经安装在系统上，并带有一个队列管理器、一个请求队列和一个应答队列。 - Dispatcher? manages an Activation Queue of service requests that are pending execution; it decides which request to de-queue next and execute on a Service Delegate object that implements the request.
Dispatcher&管理等待执行的服务请求的激活队列；它决定接下来哪个请求退出队列并在实现该请求的ServiceDelegate对象上执行。 - In this case, we may not want to queue every incoming request to our work queue, because the tasks queued for execution may consume too many system resources and cause resource starvation.
在这种情形下，我们可能不想将每个到来的请求都排队到我们的工作队列，因为排在队列中等待执行的任务可能会消耗太多的系统资源并引起资源缺乏。 - Each servlet listens on a specific JMS queue for request messages, and upon receiving a request will perform its specified action, placing response messages on a single shared outbound response queue.
每个servlet都监听特定的JMS队列以获取需求信息，一旦收到了该信息就执行指定的操作，将回复信息放置在单一的共享输出的响应队列中。 - In this first use case, a single group fruit was granted access to connect to the queue manager, put and inquire on the request queue, and get, browse, and inquire on the reply queue.
在第一个用例中，单一分组fruit授予了连接到队列管理器、查询请求队列以及获取、浏览和查询回复队列的权限。 - Notice that the flows for the database and queue storage types use custom mediation primitives to record only the fact that the request has arrived.
注意，数据库和队列存储类型的流使用自定义中介原语来记录请求到达的事实。 - The thread will in fact attempt another remove() call on the queue and will become blocked until the next available request.
事实上，线程会对队列尝试另一个remove（）调用，并变成阻塞，直到下一个请求可用。 - Create queue destinations for the request and response messages respectively on one service integration bus: REQUESTQ and RESPONSEQ.
在服务集成总线上，分别创建请求队列目的地和响应消息：REQUESTQ和RESPONSEQ。 - The work request queue size parameter specifies the size of the work request queue, a buffer that holds scheduled work objects.
workrequestqueuesize参数指定工作请求队列的大小，这是一个容纳计划内工作对象的缓冲。 - To implement file consistency, we have designed a queue that is used to place the request using first-come-first-served basis.
为保持文件一致性，我们设计了一个队列，用于放置请求，并按照先到先服务的原则。 - If several keystroke requests are in the queue when a previous request returns, only the last will go to the server.
如果当之前的请求返回时队列中有多个按键请求，那么只将最新的按键请求发送到服务器。 - That is, time in the queue plus time to actually service the request on the application server should be less than the configured service goal, assuming sufficient capacity exists.
也就是说，如果有足够的处理能力，在队列中的时间加上在应用服务器上实际为请求服务的时间应该小于配置的服务目标。 - In the next few steps, we will set up the Queue connection factories for the request queue and then create the reply queue connection factory.
在接下来的几个步骤中，我们将为请求队列设置队列连接工厂，然后创建应答队列连接工厂。 - Imports do not use an MDB to receive responses and can be configured to use a single reply queue or one temporary reply queue per request via the JMS URL specified for the import binding in the WebSphere Integration Developer tool.
导入不使用MDB来接收响应，可配置为通过在WebSphereIntegrationDeveloper工具中为导入绑定指定的JMSURL，使用单个回复队列或为每个请求使用一个临时回复队列。 - Imports don't use an MDB to receive responses and can be configured to use a single reply queue or one temporary reply queue per request.
导入并不使用MDB接收响应，可以将其配置为对每个请求使用单个应答队列或者一个临时应答队列。 - Note that a regular JMS application would read the name of the response queue from the ReplyTo field in the request message.
（请注意，常规JMS应用程序将从请求消息中的ReplyTo字段中读取响应队列的名称）。 - This avoids the common silliness of constantly putting a request on a successor stage's queue, then immediately invoking that successor stage and dequeuing the request again;
这样避免不断把请求放在下一阶段的队列里，紧接着又从该队列取出这个请求来执行。 - Compared to the traditional load balancing algorithms that consider only the running queue, the load balancing algorithms which consider the I/ O request queue can get better performance;
与传统的只考虑CPU就绪队列的负载平衡算法相比，考虑了各种I/O请求队列的负载平衡算法可以取得更好的性能； - It aggregates multi-aspect factors to adjust self-adaptively such as average length of request queue, temporary length of request queue, the relations of every request and the loading etc.
该算法综合了平均请求队列长度、瞬时请求队列长度、请求之间的关系以及负载情况等多方面的因素自适应调整。 - · The status transfer of request in queue is analyzed deeply, for sketching the status transfer pattern of request in pipe queue and batch queue.
对请求在队列中的状态迁移进行了深入分析，勾画了请求在管道队列以及批处理队列中的状态迁移模式。 - In terms of factual consumed time of each queue during last frame, time quota of burst request or radar event in next frame is adaptively adjusted.
并且根据上帧中各队列事件的实际用时，自适应地调整下一帧中波束请求或雷达事件所占的时间配额。 - CPU queue length, disk request queue length and task progress rate are chosen to weigh the resource performance. A load cluster method based on connected subgraph is proposed to decide whether task migration is needed and the sender and receivers of it.
选取CPU就绪队列长度、磁盘请求队列长度和任务进度三个负载参数衡量资源性能，提出了基于连通分图的负载聚类方法以决定是否需要任务迁移及迁移任务的发送者和接收者。 - In the queue registers, every transfer request is subdivided into read requests and write requests. Read requests are controlled by read transfer state machine, write requests are controlled by write transfer state machine.
在队列寄存器组中将传输请求分为读请求和写请求，分别由读传输状态机和写传输状态机控制执行。